Configure a message map (SHARED)

An EDI message map is a mapping file created using the GoXML mapping utility licensed from OpenText Output Transformation (formerly Xenos). This file controls the mapping process of data between the EDI message and N4. For inbound EDI, the mapping file determines where the data from the EDI message is posted in N4. For outbound EDI, the mapping file determines where the data extracted from N4 is written in the EDI message.

The following diagram displays the function of the mapping file for both inbound and outbound EDI.

A mapping file matches the segments in an EDI interchange with corresponding fields in the database.

The mapping file references a data dictionary file, which defines the structure of the EDI message. N4 provides a standard set of mapping files and data dictionary files that you can customize as necessary by using the GoXML mapping utility. For information about using the GoXML mapping utility from OpenText Output Transformation, see the documentation that comes with the product, or go to http://www.opentext.com/.

If an EDI message map references a Navis standard mapping file and data dictionary file, a bullet displays in the Built-In column on the Message Map tab in the Message Type form (on page 1).

You can add, edit, or delete a EDI message map on this tab.

If you edit an EDI message map, you can export the schema files for the selected EDI message type to use as a reference.

To configure a message map:

1. Configure the message type (on page 1).

2. Click to open a blank EDI Message Map form.

3. In the Map Id field, enter a name for the message map. For example, for an outgoing BAPLIE message, this could be BAPLIE_15_OUT. You can create multiple maps for an EDI message because trading partners may use different implementations of the EDI message.

4. From the Direction list, select Send or Receive.

5. To import the data dictionary file that defines the EDI message structure, click Import DIC.

6. In the Import XML Configuration dialog box, select the data dictionary file and click Open.

XML data dictionary files have the extension .dic, and flat text dictionary files have the extension .fxd.

When successful, the EDI Message Map Dictionary File field displays --loaded-- in the text box to indicate that a data dictionary file is linked with the EDI message map.

7. To import the mapping file that defines the EDI map, click Import MGT.

8. In the Import XML Configuration dialog box, select the mapping file and click Open.

Mapping files have the extension .mgt.

When the import is successful, the EDI Message Map File field displays --loaded-- in the text box to indicate that a mapping file is linked with the EDI message map.

9. Optionally, in the Description field, enter a description of the map.

10. Click Save. The new message map appears in the list on the Message Map tab. The Built-In column should be blank. Even if you imported (without changes) the data dictionary and message map that you exported from a "Built-In" message map, N4 does not mark them as "Built-In" because it does not compare the files.

11. In the EDI Message Type window, click Close.

You can now create an outbound stowplan session (on page 1) or send vessel statistics.

Notes

To add or update all of the supported EDI message types and respective standard EDI message maps, see Set-up Database view in the N4 client Help topics, or go to N4 client Administration DBA Set-up Database Set-up Database view and click the Help button.